Inferring physical layer connection status of generic cables from planned single-end connection events

ABSTRACT

A work order is generated. The work order comprises a first work order step specifying that a port of a first network element is to be connected to a port of a second network element using a cable. The first and second network elements are configured to detect when connections are made at the specified ports of the first network element and the second network element. A management system is configured to update information it maintains to indicate that there is a connection between the specified port of the first network element and the specified port of the second network element if connections made at the specified ports of the first and second network elements are detected during a period in which the first work order step of the first work order is expected to be performed. A similar technique can be used for disconnecting a cable.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 14/458,974 titled “INFERRING PHYSICAL LAYERCONNECTION STATUS OF GENERIC CABLES FROM PLANNED SINGLE-END CONNECTIONEVENTS” filed on Aug. 13, 2014, which claims the benefit of U.S.Provisional Patent Application Ser. No. 61/865,709, filed on Aug. 14,2013, both of which are hereby incorporated herein by reference.

BACKGROUND

Various types of physical layer management (PLM) technology can be usedto track cross connections made at patch panels or otherinter-connection devices. Generally, such PLM technology includesfunctionality to obtain information about what is connected to eachservice port of a patch panel or other inter-connection device and tocommunicate that information back to a management system. The managementsystem stores the information and makes it available for variouspurposes (such as tracing connections and carrying out electronic workorders that specify how one or more connections are to be moved, added,or otherwise changed).

One type of PLM technology makes use of an Electrically ErasableProgrammable Read-Only Memory (EEPROM) or other storage device that isintegrated with or attached to a connector on a cable. The storagedevice is used to store an identifier for the cable or connector alongwith other information. The port (or other connector) into which theassociated connector is inserted is configured to read the informationstored in the EEPROM when the connector is inserted into the port ofpatch panel or other network element.

Another type of PLM technology makes use of radio frequencyidentification (RFID) tags and readers. With RFID technology, an RFIDtag is attached to or integrated with a connector on a cable. The RFIDtag is used to store an identifier for the cable or connector along withother information. The RFID tag is typically then read using an RFIDreader after the associated connector is inserted into a port (or otherconnector) of a patch panel or other network element.

Both of the PLM technologies described above are examples of“identifier-based” PLM technology that is configured to work withnon-standard cables from which identifier or other information can beread. The information read from the cables is used to identify and trackconnections. However, such PLM technologies are not able to read suchinformation from standard cables and, therefore, typically are not ableto identify and track connections made using standard cables.

SUMMARY

One embodiment is directed to a method comprising generating a firstwork order comprising a first work order step specifying that a port ofa first network element is to be connected to a port of a second networkelement using a cable. The method further comprises detecting, using thefirst network element, when a connection is made at the specified portof the first network element and detecting, using the second networkelement, when a connection is made at the specified port of the secondnetwork element. The method further comprises, if the first networkelement detects a connection made at the specified port of the firstnetwork element during a period in which the first work order step ofthe first work order was expected to be performed and the second networkelement detects a connection made at the specified port of the secondnetwork element during the period in which the first work order step ofthe first work order was expected to be performed, updating a managementsystem to indicate that the specified port of the first network elementis connected to the specified port of the second network element.

Another embodiment is directed to a method of identifying adisconnection of a specified port of a first network element from aspecified port of a second network element. The method comprises, ifafter the port of the first network element is connected to the port ofthe second network element using a cable: generating a first work ordercomprising a first work order step specifying that the port of the firstnetwork element is to be disconnected from the port of the secondnetwork element; detecting, using the first network element, when adisconnection is made at the specified port of the first networkelement, and detecting, using the second network element, when adisconnection is made at the specified port of the second networkelement. The method further comprises, if the first network elementdetects a disconnection made at the specified port of the first networkelement during a period in which the first work order step of the firstwork order was expected to be performed and the second network elementdetects a disconnection made at the specified port of the second networkelement during the period in which the first work order step of thefirst work order was expected to be performed, updating a managementsystem to indicate that the specified port of the first network elementis not connected to the specified port of the second network element.

Another embodiment is directed to a system comprising a first networkelement comprising at least one port. The first network element isconfigured to detect when a cable is connected to the port of the firstnetwork element. The system further comprises a second network elementcomprising at least one port. The second network element is configuredto detect when a cable is connected to the port of the second networkelement. The system further comprises a management systemcommunicatively coupled to the first network element and the secondnetwork element. The management system is configured to generate a firstwork order comprising a first work order step specifying that the portof the first network element is to be connected to the port of thesecond network element using a cable. The management system isconfigured to update information maintained by the management system toindicate that the specified port of the first network element isconnected to the specified port of the second network element if themanagement system receives a message indicating that a connection wasdetected at the specified port of the first network element during aperiod in which the first work order step of the first work order isexpected to be performed and receives a message indicating that aconnection was detected at the specified port of the second networkelement during the period in which the first work order step of thefirst work order was expected to be performed.

Another embodiment is directed to a system comprising a first networkelement comprising at least one port. The first network element isconfigured to detect when a cable is disconnected from the port of thefirst network element. The system further comprises a second networkelement comprising at least one port. The second network element isconfigured to detect when a cable is disconnected from the port of thesecond network element. The system further comprises a management systemcommunicatively coupled to the first network element and the secondnetwork element. The management system is configured to generate a firstwork order comprising a first work order step specifying that the portof the first network element is to be disconnected from the port of thesecond network element. The management system is configured to updateinformation maintained by the management system to indicate that thespecified port of the first network element has been disconnected fromthe specified port of the second network element if the managementsystem receives a message indicating that a disconnection was detectedat the specified port of the first network element during a period inwhich the first work order step of the first work order was expected tobe performed and receives a message indicating that a disconnection wasdetected at the specified port of the second network element during theperiod in which the first work order step of the first work order wasexpected to be performed.

Another embodiment is directed to a program product for identifying aconnection between a specified port of a first network element and aspecified port of a second network element, tangibly stored on anon-transitory storage medium. The program product comprisinginstructions operable to cause at least one programmable processor togenerate a work order comprising a work order step specifying that thespecified port of the first network element is to be connected to thespecified port of the second network element using a cable. The programproduct further comprising instructions operable to cause at least oneprogrammable processor to, in connection with a connection being made atthe specified port of the first network element specified in the workorder step, receiving information indicating that the connection hasbeen made at the specified port of the first network element and, inconnection with a connection being made at the specified port of thesecond network element, receiving information indicating that theconnection has been made at the specified port of the second networkelement. The program product further comprising instructions operable tocause at least one programmable processor to, if information is receivedindicating that a connection has been made at the specified port of thefirst network element during a period in which the work order step ofthe work order is expected to be performed and information is receivedindicating that a connection has been made at the specified port of thesecond network element during the period in which the work order step ofthe work order is expected to be performed, updating connectioninformation for the first network element and the second network elementto indicate that the specified port of the first network element isconnected to the specified port of the second network element.

DRAWINGS

FIG. 1 is a block diagram of one exemplary embodiment of a physicallayer management (PLM) system.

FIG. 2 illustrates one embodiment of a method of identifying aconnection made using a cable.

FIG. 3 illustrates one embodiment of a method of performing a work orderassociated with disconnecting a cable.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of one exemplary embodiment of a physicallayer management (PLM) system 100.

The PLM system 100 is used to track physical layer information relatedto a network 102. As used herein, “physical layer information” comprisesinformation about the cabling, connections, and communication links thatexist in the network 102.

In the exemplary embodiment shown in FIG. 1, the network 102 includesvarious network elements or devices to which cables are connected. Inthe exemplary embodiment shown in FIG. 1, the network 102 includes atleast some managed network elements or devices 104. As used herein, a“managed” network element or device 104 is a network element or devicethat includes some type of identifier-based physical layer management(PLM) technology 106 for automatically reading identifier and otherphysical layer information related to one or more cables that areconnected to that device 104. Examples of managed devices 104 include,without limitation, patch panels, optical distribution frames, splittertrays, switches, routers, etc., that include one or more of EEPROM-basedPLM technology and RFID PLM technology.

The network 102 also typically includes unmanaged network elements anddevices (not shown). As used herein, an “unmanaged” network element ordevice is a network element or device that does not include any such PLMtechnology.

The identifier-based PLM technology 106 included in each managed device104 is configured to read the identifier and other PLI information fromnon-standard cables 108. These non-standard cables 108 are also referredto here as “managed cables” 108.

In general, the identifier-based PLM technology 106 includes acontroller or other programmable processor 110 that is configured tocommunicate captured identifier and other physical layer information toa management system 112 over the network 102. In the example shown inFIG. 1, each controller 110 is communicatively coupled to the network102 and the management system 112 by including a respective “management”or “non-service” port 114 in the associated managed device 104. Eachmanagement port 114 is separate from the “service” ports 116 of thatdevice 104. However, the controller 110 in the managed devices 104 canbe communicatively coupled to the network 102 using one or more of the“service” ports 116. Power can be supplied to the identifier-based PLMtechnology 106 in each managed device 104 in various ways (for example,by connecting the managed device 104 to the standard AC power grid,using Power-Over-Ethernet technology, or in other ways).

Unmanaged cables 118 can also be used with the managed network elementsor devices 104. There are two types of “unmanaged” cables 118. One typeof unmanaged cable 118 is a standard cable that is not speciallyconfigured to be used with any type of identifier-based PLM technology.The other type of unmanaged cable 118 is a managed cable that isconfigured to be used with a different and incompatible type ofidentifier-based PLM technology. For example, a cable including onlyRFID-based PLM technology when connected to a managed device configuredfor use with EEPROM-based PLM technology is considered an unmanagedcable, and, similarly, a cable including only EEPROM-based PLMtechnology when connected to a managed device configured for use withRFID-based PLM technology is considered an unmanaged cable.

Examples of cables 108 and 118 include, without limitation, CAT-5, 6,and 7 twisted-pair cables having modular connectors or plugs attached toboth ends (in which case, the service ports 116 are implemented usingcompatible modular jacks) or optical cables having SC, LC, FC, LX.5,MTP, or MPO connectors (in which case, the service ports 116 areimplemented using compatible SC, LC, FC, LX.5, MTP, or MPO connectors oradapters). The techniques described here can be used with other types ofconnectors and cables including, for example, cables terminated with BNCconnectors, F connectors, DSX jacks and plugs, bantam jacks and plugs,and MPO and MTP multi-fiber connectors and adapters.

Each of the managed network elements or devices 104 is configured todetect when a cable 108 or 118 is attached or connected to that managednetwork element or device 104, regardless of whether the cable is amanaged cable 108 or an unmanaged cable 118. For example, each serviceport 116 of the managed device 104 can include one or more electricalcontacts or switches that are configured to open or close an electricalcircuit when a connector attached to a cable 108 or 118 is inserted intothat port 116. This detection can be implemented in other ways (using,for example, sensors or mechanical, electrical, or other switches).Also, it is important to note that this detection is implemented out ofband. That is, this detection is not implemented using the standardfunctionality for communicating data over the service ports 116.

More specifically, in the exemplary embodiment shown in FIG. 1, each ofthe managed devices 104 comprises a patch panel (and is also referred tohere as “managed patch panel” 104). Each managed patch panel 104 isdescribed here, in this exemplary embodiment, as being designed for usewith copper twisted-pair CAT-5, 6, and 7 cables typically used toimplement ETHERNET local area networks.

Each managed patch panel 104 implements EEPROM-based PLM technology 106.More specifically, in this exemplary embodiment, each managed cable 108includes a respective storage device (such as an EEPROM) 120 that isattached or integrated into (or is otherwise associated with) aconnector 122 attached to each end of that managed cable 108. Eachstorage device 120 comprises an interface 124 by which power is providedto the storage device 120 and data is read from and written to thestorage device 120. In this example, the storage device interface 124comprises a set of contacts (for example, a power contact for supplyingpower to the storage device 120, a ground contact for supplying a groundto the storage device 120, and a serial data contact for communicatingdata to and from the electronic storage device 120 using a serial busprotocol such as the UNI/O bus protocol). In one implementation of thisembodiment, the electronic storage device 120 and the interface 124 areimplemented using the QUAREO™ electronic identifier technologycommercially available from TE Connectivity. The electronic storagedevice 120 and the interface 124 can be implemented in other ways.

In this exemplary embodiment, the identifier-based PLM technology 106included in each managed patch panel 104 includes a correspondingstorage device interface 128 for each service port 116 of that managedpatch panel 104. For each service port 116, the corresponding storagedevice interface 128 is configured to couple a storage device 120attached to a connector 122 inserted into that service port 116 to thecontroller 110 in the managed patch panel 104 so that the controller 110is able read information stored in the storage device 120 and/or writeinformation to the storage device 120. The storage device interface 128is compatible with the storage device interface 124 used on the storagedevice 120. In this example, each storage device interface 128 comprisesa set of contacts that corresponds to the set of contacts used on eachconnector 122 (for example, including power, ground, and serial datacontacts). Each contact in the interface 128 of the patch panel 108 isconfigured to come into physical contact with a corresponding contactused on the connector 122 and create an electrical connectiontherebetween.

In the exemplary embodiment shown in FIG. 1, one or more of the contactsin the storage device interface 128 for each service port 116 isconfigured in such a way to change the state of an electrical circuitwhen a connector is inserted into that service port 116. For example, aconductor used to implement such a contact can be configured andmechanically biased to be in a first position that is associated with afirst state (for example, an open state where an electrical connectionis not made) when no connector is inserted into the correspondingservice port 116, and can be configured and mechanically biased to bemoved into a second position that is associated with a second state (forexample, a closed state in which an electrical connection is made) whena connector is inserted into the corresponding service port 116. Acircuit (not shown) for each such contact is used to develop a firstlogic state on an input/output (I/O) line associated with that contactwhen that contact is in the first state and to develop a second logicstate on the input/output line associated with that contact when thatcontact is in a second state. Moreover, each such circuit can also beconfigured to enable data other than the logic state of the contact tobe communicated over that I/O line (for example, each such I/O line canbe used to read data from and/or write data to a storage device 120 overthat I/O line).

The controller 110 monitors (for example, by polling) the logic state ofthe various I/O lines to determine when a connector has been insertedinto or removed from a given service port 116. When such an insertion orremoval occurs, the controller 110 sends a message to the managementsystem 112 informing the management system 112 of that insertion orremoval event. Also, when a connector 122 attached to a managed cable108 is inserted into a service port 116 of a managed patch panel 104,the corresponding controller 110 reads the identifier and otherinformation stored in the storage device 120 attached to or integratedinto that connector 122 and communicates that information to themanagement system 112. The management system 112, when it receives suchinformation read from a storage device 120 associated with a connector122, stores and/or updates information in a database or other data store132 maintained by the management system 112. This information is used toidentify and track connections that are made between the service ports116 of the managed patch panels 104.

In this example, each managed patch panel 104 includes one or more lightemitting diodes (LEDs) (or other visual indicators) 134 that areassociated with each service port 116 of the managed patch panel 104.Each LED 134 is coupled to the controller 110 in the managed patch panel104 so that the controller 110 (more specifically, the softwareexecuting on the controller 110) can actuate the LEDs 134 (for example,by turning the LEDs 134 on or off or flashing or changing the color ofthe LEDs 134).

In the exemplary embodiment shown in FIG. 1, the management system 112is implemented as software that executes on one or more computers 136.

In the exemplary embodiment shown in FIG. 1, each computer 136 comprisesone or more programmable processors 138 for executing the software. Thesoftware comprises program instructions that are stored (or otherwiseembodied) on or in an appropriate non-transitory storage medium or media140 (such as flash or other non-volatile memory, magnetic disc drives,and/or optical disc drives) from which at least a portion of the programinstructions are read by the programmable processor 138 for executionthereby. Although the storage media 140 is shown in FIG. 1 as beingincluded in, and local to, the respective computer 136, it is to beunderstood that remote storage media (for example, storage media that isaccessible over the network 102) and/or removable media can also beused. Each computer 136 also includes memory 142 for storing the programinstructions (and any related data) during execution by the programmableprocessor 138. Memory 142 comprises, in one implementation, any suitableform of random access memory (RAM) now known or later developed, such asdynamic random access memory (DRAM). In other embodiments, other typesof memory are used. Each computer 136 also includes one or more networkinterfaces 144 for communicatively coupling the computer 136 to thenetwork 102.

In the example shown in FIG. 1, the management system 112 furtherincludes an electronic work order application 146. The electronic workapplication 146 is used to construct electronic work orders 148. Eachelectronic work 148 specifies one or more steps that are to be carriedout by a technician at a particular location. For example, an electronicwork order 148 can indicate that one or more connections implementedusing the ports 116 of the managed patch panels 104 should be added,removed, and/or changed. For steps that involve adding, removing, and/orchanging connections made at the ports 116 of the managed patch panels104, the information that is read from the associated storage devices120 by the identifier-based PLM functionality 106 in the patch panels104 and communicated to the management system 112 can be used by theelectronic work order application 146 to verify that the specifiedconnection has been added, removed, and/or changed correctly.

The LEDs 134 associated with the service ports 116 of the managed patchpanels 104 can be actuated in order to guide a technician in carryingout the steps of electronic work orders 148.

In this example, each electronic work order 148 is communicated to asmartphone 150 (or similar device) that is carried by a technician thathas been assigned to carry out that electronic work order 148. In thisexample, the smartphone 150 is configured to execute a mobileapplication 152. The mobile application 152 is configured to communicatewith the electronic work order application 146 and the management system112 and to receive the electronic work orders 148. The mobileapplication 152 comprises program instructions that are stored (orotherwise embodied) on or in an appropriate non-transitory storagemedium or media from which at least a portion of the programinstructions are read by at least one programmable processor included inthe smartphone 150 for execution thereby.

Each electronic work order 148 can be communicated wirelessly to thesmartphone 150 over the Internet (for example, via a cellular orwireless local area network to which the smartphone 150 is wirelesslyconnected). Each electronic work order can also be communicated to thesmartphone 150 in other ways (for example, using a wired connection withthe smartphone 150).

As noted above, the identifier and other information read from themanaged cables 108 is used to identify and track connections made usingmanaged cables 108. However, techniques for identifying and trackingconnections that depend on using identifier and other information readfrom managed cables 108 cannot be used with unmanaged cables 118.

FIG. 2 illustrates one embodiment of a method 200 of identifying aconnection made using a cable. The exemplary embodiment of method 200shown in FIG. 2 is described here as being implemented using the system100 shown in FIG. 1, though it is to be understood that otherembodiments can be implemented in other ways. Moreover, the blocks ofthe flow diagram shown in FIG. 2 have been arranged for ease ofexplanation; however, it is to be understood that this arrangement ismerely exemplary, and it should be recognized that the processingassociated with method 200 (and the blocks shown in FIG. 2) can occur inany order (for example, using standard event-driven programmingtechniques).

Method 200 can be used with either a managed cable 108 or an unmanagedcable 118, though method 200 is especially useful for identifying andtracking connections made with an unmanaged cable 118 since theidentifier-based PLM technology that is otherwise included in thenetwork 102 is typically designed to identify and track connections madewith managed cables 108 and is typically not able to identify and trackconnections made with unmanaged cables 118. Accordingly, the followingdescription of method 200 is described below as using an unmanaged cable118, though it is to be understood that method 200 can also be used withmanaged cables 108 (though it likely would be preferable to use theidentifier-based PLM technology to identify and track connections madeusing managed cables 108).

Method 200 comprises generating a work order 148 that includes a workorder step specifying that a service port 116 of a first managed patchpanel 104-A is to be connected to a service port 116 of a second managedpatch panel 104-B using an unmanaged cable 118 (block 202). In thisexample, the electronic work order application 146 is used to create theelectronic work order 148. The electronic work order 148, in thisexample, is communicated to a mobile application 152 executing on asmartphone 150 used by a technician that is to carry out the electronicwork order 148. The electronic work order 148 can be wirelesslycommunicated from the electronic work order application 146 to thesmartphone 150 (for example, using a cellular or wireless local areanetwork communication link) or using a wired connection to the Internet,a local area network, or a direct connection between the smartphone 150and the computer 136 on which the electronic work order application 146executes.

After the electronic work order 148 has been downloaded to the mobileapplication 152 on the smartphone 150, a technician can use the mobileapplication 152 to view the electronic work order 148 and the stepsincluded in the electronic work order 148. After the technician hastraveled to the location where the first and second managed patch panels104-A and 104-B are installed, the technician can use the mobileapplication 152 executing on the smartphone 150 to assist the technicianin carrying out the steps in the work order 148.

When the technician is ready to perform the step noted above inconnection with block 202, the technician activates that step of thework order (block 204). Activating the work order step involvessignaling to the mobile application 152 executing on the smartphone 150and the management system 112 that the technician is ready to performthat work order step. The technician can do this by providing a suitableinput to the mobile application 152 using the smartphone 150. When themobile application 152 receives such an input, the mobile application152 sends a message to the management system 112 that indicates that thetechnician is ready to perform the work order step.

In response to the work order step being activated, the managementsystem 112 illuminates (or otherwise actuates) the LEDs 134 associatedwith the specified service ports 116 (block 206). That is, themanagement system 112 sends a message to the controller 110 in the firstmanaged patch panel 104-A indicating that the LED 134 associated withthe specified service port 116 included in the first managed patch panel104-A should be illuminated. In response to receiving such a message,the controller 110 included in the first managed patch panel 104-Ailluminates (or otherwise actuate) that LED 134. The same thing is donefor the specified service port 116 that is included in the secondmanaged patch panel 104-B. That is, the management system 112 sends amessage to the controller 110 in the second managed patch panel 104-Bindicating that the LED 134 associated with the specified service port116 included in the second managed patch panel 104-B should beilluminated. In response to receiving such a message, the controller 110included in that second managed patch panel 104-B illuminates (orotherwise actuate) that LED 134.

Illuminating the LEDs 134 associated with the specified service ports116 provides the technician with a visual indication that is intended toassist the technician in locating the specified service ports 116.However, it is to be understood that providing such a visual indicationis optional, and it is to possible for the technician to locate thespecified service ports 116 in other ways (for example, by looking forlabels that are included on the managed patch panels 104-A and 104-Bthat identify each of the specified service ports 116).

Then, the technician can insert the connector attached to one end of theunmanaged cable 118 into one of the specified service ports 116 andinsert the connector attached to the other end of the unmanaged cable118 into one of the specified service ports 116. The order in which theconnections are made can be (but need not be) specified in the workorder step.

Method 200 comprises detecting, using the first managed patch panel104-A, when a connector insertion is made at the specified service port116 included in the first managed patch panel 104-A (block 208) anddetecting, using the second managed patch panel 104-B, when a connectorinsertion is made at the specified service port 116 included in thesecond managed patch panel 104-B (block 210). As noted above, thecontroller 110 in each of the managed patch panels 104-A and 104-Bmonitors the logic state of the various I/O lines used to couple the PLMtechnology 106 to the controller 110 in order to determine when aconnector has been inserted into or removed from any of the serviceports 116. When a connector is inserted into or removed from any of theservice ports 116, the controller 110 sends a message to the managementapplication 112 notifying the management system 112 of that fact. Themessage indicates whether the event was an insertion or a removal andincludes information identifying the service port 116 and managed device104 involved. Also, the message can include information indicating whenthe particular insertion or removal occurred.

Method 200 further comprises determining if a connector insertion wasdetected at the specified service port 116 of the first managed patchpanel 104-A as occurring during a period when the work order step notedabove in connection with block 204 was expected to be performed and if aconnector insertion was detected at the specified service port 116 ofthe second managed patch panel 104-B as occurring during the period whenthe work order step was expected to be performed (checked in block 212).Method 200 further comprises, if both such insertions were detected asoccurring during the period when the work order step was expected to beperformed, updating the management system 112 to indicate that thespecified service ports 116 of the first managed patch panel 104-A andthe second managed patch panel 104-B are connected to one another (block214) and stopping the illumination (or other actuation) of the LEDs 143associated with the specified service ports 116 (block 216).

In this example, the work order step is expected to be performed whilethe work order step is activated as described above in connection withblock 204. The work order step, after initially being activated, remainsactivated until the work order step is successfully completed, thetechnician manually deactivates the work order step using the mobileapplication 152, or a predetermined period of time elapses without thestep being successfully completed.

In this example, the management system 112 is configured to check theinsertion and removal messages it receives from the controllers 110 ofthe first and second managed patch panels 104-A and 104-B. Themanagement system 112 checks to see if it has received an insertionmessage for the specified service port 116 of the first managed patchpanel 104-A that indicates that an insertion occurred at the specifiedservice port 116 while the work order step was activated. The managementsystem 112 also checks to see if it has received an insert message forthe specified port 116 of the second managed patch panel 104-B thatindicates that an insertion occurred while at the specified service port116 while the work order step was activated. If the management system112 receives both such insertion messages, the management system 112considers the work order step to have been successfully completed andupdates the information it maintains to indicate that the specifiedservice ports 116 are connected to one another. In other words, aconnection between the two specified ports 116 is inferred from thesingle-end events (insertion events in this case).

This determination can be made in real-time (for example, where thesmartphone 150 is communicatively coupled the management system 112while the technician is performing the work order step) or can be madeafter the fact by comparing and reconciling the time informationincluded in the work step activation message and any relevant insertionand removal messages.

If both such insertions were not detected as occurring while that workorder step was activated, an alarm can be raised (block 218). Themanagement system 112 can be configured to raise such an alarm in manyways. For example, the management system 112 can be configured to send amessage to the mobile application 152 indicating that the managementsystem 112 was not able to validate that the work order step wasproperly performed. Also, the management system 112 can be configured toadd an entry to a log maintained for electronic work orders, where theadded entry indicates that the management system 112 was not able tovalidate that the work order step was properly performed. Also, someother action can be taken if both of the specified insertions were notdetected as occurring while the step was activated.

By performing the processing associated with method 200, a connectionspecified in a work order step can be inferred from single-end insertionevents occurring while the work order step was activated. In this way,the management system 112 is able to capture connection informationabout unmanaged cables 118 that are used with the managed patch panels104. That is, even though an unmanaged cable 118 is used with themanaged patch panels 104 and the identifier-based PLM technology 106included in them is not able to identify a connection based onidentifier information read from the unmanaged cable 118, the managementsystem 112 is nevertheless still able to infer that a connection is madebetween the two specified ports 116 from the associated single-endinsertion events and validate that the electronic work step was properlyperformed. Also, because such events occur in the context of, and resultfrom the performance of, a step of an electronic work order, theinference of the connection has a higher degree of confidence than wouldotherwise be the case.

Similar processing can be used for the removal of an unmanaged cable118.

FIG. 3 illustrates one embodiment of a method 300 of performing a workorder associated with disconnecting a cable. The exemplary embodiment ofmethod 300 shown in FIG. 3 is described here as being implemented usingthe system 100 shown in FIG. 1, though it is to be understood that otherembodiments can be implemented in other ways. Moreover, the blocks ofthe flow diagram shown in FIG. 3 have been arranged for ease ofexplanation; however, it is to be understood that this arrangement ismerely exemplary, and it should be recognized that the processingassociated with method 300 (and the blocks shown in FIG. 3) can occur inany order (for example, using standard event-driven programmingtechniques).

As with method 200 of FIG. 2, method 300 can be used with either amanaged cable 108 or an unmanaged cable 118, though method 300 isespecially useful for identifying and tracking connections made with anunmanaged cable 118 since the identifier-based PLM technology that isotherwise included in the network 102 is typically designed to identifyand track connections made with managed cables 108 and is typically notable to identify and track connections made with unmanaged cables 118.Accordingly, the following description of method 300 is described belowas using an unmanaged cable 118, though it is to be understood thatmethod 300 can also be used with managed cables 108 (though it likelywould be preferable to use the identifier-based PLM technology toidentify and track connections made using managed cables 108).

In this example, method 300 is performed after a connection is madebetween a service port 116 of a first managed patch panel 104-A and aservice port 116 of a second managed patch panel 104-B using anunmanaged cable 118.

Method 300 comprises generating a work order 148 that includes a workorder step specifying that the service port 116 of the first managedpatch panel 104-A is to be disconnected from the service port 116 of thesecond managed patch panel 104-B (block 302). In this example, theelectronic work order application 146 is used to generate the electronicwork order 148. The electronic work order 148, in this example, iscommunicated to a mobile application 152 executing on a smartphone 150.The electronic work order 148 can be wirelessly communicated from theelectronic work order application 146 (for example, using a cellular orwireless local area network communication link) or using a wiredconnection to the Internet, local area network, or a wired directconnection between the smartphone 150 and the computer 136 on which theelectronic work order application 146 executes.

After the electronic work order 148 has been downloaded to the mobileapplication 152 on the smartphone 150, a technician can use the mobileapplication 152 to view the electronic work order 148 and the stepsincluded in the electronic work order 148. After the technician hastraveled to the location where the first and second managed patch panels104-A and 104-B are installed, the technician can use the mobileapplication 152 executing on the smartphone 150 to assist the technicianin carrying out the steps in the work order 148.

When the technician is ready to perform the step noted above inconnection with block 302, the technician activates that step of thework order (block 304). This can be done as described above inconnection with block 204 of method 200.

In response to the work order step being activated, the managementsystem 112 illuminates (or otherwise actuates) the LEDs 134 associatedwith the specified service ports 116 (block 306). This can be done asdescribed above in connection with block 206 of method 200.

Illuminating the LEDs 134 associated with the specified service ports116 is intended to provide the technician with a visual indication inorder to assist the technician in locating the specified service ports116. However, it is to be understood that providing such a visualindication is optional, and it is to possible for the technician tolocate the specified service ports 116 in other ways (for example, bylooking for labels that are included on the managed patch panels 104-Aand 104-B that identify each of the specified service ports 116).

Then, the technician can disconnect the unmanaged cable 118 from thespecified service port 116 of the first managed patch panel 104-A andfrom the specified service port 116 of the second managed patch panel104-B. The order in which the disconnections are performed can be (butneed not be) specified in the work order step.

Method 300 comprises detecting, using the first managed device 104-A,when a connector removal occurs at the specified service port 116included in the first managed device 104-A (block 308) and detecting,using the second managed patch panel 104-B, when a connector removaloccurs at the specified service port 116 included in the second managedpatch panel 104-B (block 310). As noted above, the controller 110 ineach of the managed patch panels 104-A and 104-B monitors the logicstate of the various I/O lines used to couple the PLM technology 106 tothe controller 110 in order to determine when a connector has beeninserted into or removed from any of the service ports 116. When aconnector is inserted into or removed from any of the service ports 116,the controller 110 sends a message to the management application 112notifying the management system 112 of that fact.

Method 300 further comprises determining if a connector removal wasdetected at the specified service port 116 of the first managed patchpanel 104-A as occurring during a period when the work order step notedabove in connection with block 302 was expected to be performed and if aconnector removal was detected at the specified service port 116 of thesecond managed patch panel 104-B as occurring during the period when thework order step was expected to be performed (checked in block 312).Method 300 further comprises, if both such removals were detected asoccurring during the period when the work order step was expected to beperformed, updating the management system 112 to indicate that thespecified service ports 116 of the first managed patch panel 104-A andthe second managed patch panel 104-B are not connected to one another(block 314) and stopping the illumination (or other actuation) of theLEDs 143 associated with the specified service ports 116 (block 316).

In this example, the work order step is expected to be performed whilethe work order step is activated as described above in connection withblock 304. The work order step, after initially being activated, remainsactivated until the work order step is successfully completed, thetechnician manually deactivates the work order step using the mobileapplication 152, or a predetermined period of time elapses without thestep being successfully completed.

In this example, the management system 112 is configured to check theinsertion and removal messages it receives from the controllers 110 ofthe first and second managed patch panels 104-A and 104-B. Themanagement system 112 checks to see if it has received a removal messagefor the specified service port 116 of the first managed patch panel104-A that indicates that a removal occurred at the specified serviceport 116 while the work order step was activated. The management system112 also checks to see if it has received a removal message for thespecified port 116 of the second managed patch panel 104-B that indicatethat a removal occurred at the specified service port 116 while the workorder step was activated. If the management system 112 receives bothsuch removal messages, the management system 112 considers the workorder step to have been successfully completed and updates theinformation it maintains to indicate that the specified service ports116 are not connected to one another. In other words, the disconnectionof the two specified ports 116 is inferred from the single-end events(removal events in this case).

This determination can be made in real-time (for example, where thesmartphone 150 is communicatively coupled the management system 112while the technician is performing the work order step) or can be madeafter the fact by comparing and reconciling the time informationincluded in the work step activation message and any relevant insertionand removal messages.

If both such removals were not detected as occurring while that workorder step was activated, an alarm can be raised (block 318). Themanagement system 112 can be configured to raise such an alarm in manyways (for example, the ways noted above in connection with block 216 ofFIG. 2).

By performing the processing associated with method 300, a disconnectionspecified in a work order step can be inferred from single-end removalevents occurring while the work order step was activated. In this way,the management system 112 is able to capture disconnection informationabout unmanaged cables 118 that are used with the managed patch panels104. That is, even though an unmanaged cable 118 is used with themanaged patch panels 104 and the identifier-based PLM technology 106included in them is not able to identify a disconnection based onidentifier information read from the unmanaged cable 118, the managementsystem 112 is nevertheless still able to infer that a disconnection ofthe two specified ports 116 occurred from the associated single-endremovals events and validate that the electronic work step was properlyperformed. Also, because such events occur in the context of, and resultfrom the performance of, a step of an electronic work order, theinference of the disconnection has a higher degree of confidence thanwould otherwise be the case.

Although methods 200 and 300 are shown and described separately for easeof explanation, it is to be understood that the processing of method 200and 300 can be combined in various ways. Also, as noted above, theblocks of the flow diagrams shown in FIGS. 2 and 3 have been arrangedfor ease of explanation; however, it is to be understood that thisarrangement is merely exemplary, and it should be recognized that theprocessing associated with methods 200 and 300 (and the blocks shown inFIGS. 2 and 3) can occur in any order (for example, using standardevent-driven programming techniques).

Moreover, although description of method 200 and 300 refer to the“insertion” and “removal” of connectors, respectively, from thespecified service ports, it is to be understood that the methods 200 and300 can be implemented using other ways of connecting and disconnecting,respectively, a cable from the specified managed network element.

Also, although the exemplary embodiment shown in FIG. 1 is describedabove as being implemented using managed patch panels 104 configured foruse with CAT-5, CAT-6, and CAT-7 twisted-pair copper cables andEEPROM-based PLM technology, it is to be understood that the techniquesdescribed here can be used with other managed network elements, cables,and PLM technology (such as, for example, optical distribution frames,splitter trays, or patch panels configured for use with fiber opticcables and/or using RFID-based PLM technology).

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications to the described embodiments maybe made without departing from the spirit and scope of the claimedinvention.

EXAMPLE EMBODIMENTS

Example 1 includes a method comprising: generating a first work ordercomprising a first work order step specifying that a port of a firstnetwork element is to be connected to a port of a second network elementusing a cable; detecting, using the first network element, when aconnection is made at the specified port of the first network element;detecting, using the second network element, when a connection is madeat the specified port of the second network element; and if the firstnetwork element detects a connection made at the specified port of thefirst network element during a period in which the first work order stepof the first work order was expected to be performed and the secondnetwork element detects a connection made at the specified port of thesecond network element during the period in which the first work orderstep of the first work order was expected to be performed, updating amanagement system to indicate that the specified port of the firstnetwork element is connected to the specified port of the second networkelement.

Example 2 includes the method of Example 1, further comprising: if afterconnecting the specified port of the first network element to thespecified port of the second network element using the cable: generatinga second work order comprising a second work order step specifying thatthe specified port of the first network element is to be disconnectedfrom the specified port of the second network element; detecting, usingthe first network element, when a disconnection is made at the specifiedport of the first network element; detecting, using the second networkelement, when a disconnection is made at the specified port of thesecond network element; and if the first network element detects adisconnection made at the specified port of the first network elementduring a period in which the second work order step of the second workorder was expected to be performed and the second network elementdetects a disconnection made at the specified port of the second networkelement during the period in which the second work order step of thesecond work order was expected to be performed, updating a managementsystem to indicate that the specified port of the first network elementis not connected to the specified port of the second network element.

Example 3 includes the method of any of the Examples 1-2, wherein thecable comprises an unmanaged cable.

Example 4 includes the method of any of the Examples 1-3, wherein thecable comprises at least one of a fiber optic cable and a copper cable.

Example 5 includes the method of any of the Examples 1-4, wherein thefirst network element and the second network element comprise first andsecond managed network elements, respectively.

Example 6 includes the method of any of the Examples 1-5, wherein thefirst and second network elements comprise at least one of a patchpanel, an optical distribution frame, a splitter tray, a switch, arouter.

Example 7 includes the method of any of the Examples 1-6, wherein eachof the first and second network elements includes at least one ofEEPROM-based PLM technology and RFID PLM technology.

Example 8 includes a method of identifying a disconnection of aspecified port of a first network element from a specified port of asecond network element, the method comprising: if after the port of thefirst network element is connected to the port of the second networkelement using a cable: generating a first work order comprising a firstwork order step specifying that the port of the first network element isto be disconnected from the port of the second network element;detecting, using the first network element, when a disconnection is madeat the specified port of the first network element; detecting, using thesecond network element, when a disconnection is made at the specifiedport of the second network element; and if the first network elementdetects a disconnection made at the specified port of the first networkelement during a period in which the first work order step of the firstwork order was expected to be performed and the second network elementdetects a disconnection made at the specified port of the second networkelement during the period in which the first work order step of thefirst work order was expected to be performed, updating a managementsystem to indicate that the specified port of the first network elementis not connected to the specified port of the second network element.

Example 9 includes a system comprising: a first network elementcomprising at least one port, wherein the first network element isconfigured to detect when a cable is connected to the port of the firstnetwork element; a second network element comprising at least one port,wherein the second network element is configured to detect when a cableis connected to the port of the second network element; and a managementsystem communicatively coupled to the first network element and thesecond network element; wherein the management system is configured togenerate a first work order comprising a first work order stepspecifying that the port of the first network element is to be connectedto the port of the second network element using a cable; and wherein themanagement system is configured to update information maintained by themanagement system to indicate that the specified port of the firstnetwork element is connected to the specified port of the second networkelement if the management system receives a message indicating that aconnection was detected at the specified port of the first networkelement during a period in which the first work order step of the firstwork order is expected to be performed and receives a message indicatingthat a connection was detected at the specified port of the secondnetwork element during the period in which the first work order step ofthe first work order was expected to be performed.

Example 10 includes the system of Example 9, wherein the managementsystem is configured to generate a second work order comprising a secondwork order step specifying that the port of the first network element isto be disconnected from the port of the second network element; whereinthe first network element is configured to detect when a disconnectionis made at the specified port of the first network element; wherein thesecond network element is configured to detect when a disconnection ismade at the specified port of the second network element; and whereinthe management system is configured to update information maintained bythe management system to indicate that the specified port of the firstnetwork element has been disconnected from the specified port of thesecond network element if the management system receives a messageindicating that a disconnection was detected at the specified port ofthe first network element during a period in which the second work orderstep of the second work order was expected to be performed and receivesa message indicating that a disconnection was detected at the specifiedport of the second network element during the period in which the secondwork order step of the second work order was expected to be performed.

Example 11 includes the system of any of the Examples 9-10, wherein thecable comprises an unmanaged cable.

Example 12 includes the system of any of the Examples 9-11, wherein thecable comprises at least one of a fiber optic cable and a copper cable.

Example 13 includes the system of any of the Examples 9-12, wherein thefirst network element and the second network element comprise first andsecond managed network elements, respectively.

Example 14 includes the system of any of the Examples 9-13, wherein thefirst and second network elements comprise at least one of a patchpanel, an optical distribution frame, a splitter tray, a switch, arouter.

Example 15 includes the system of any of the Examples 9-14, wherein eachof the first and second network elements includes at least one ofEEPROM-based PLM technology and RFID PLM technology.

Example 16 includes the system of any of the Examples 9-15, wherein themanagement system is configured to send the first work order to a mobiledevice.

Example 17 includes a system comprising: a first network elementcomprising at least one port, wherein the first network element isconfigured to detect when a cable is disconnected from the port of thefirst network element; a second network element comprising at least oneport, wherein the second network element is configured to detect when acable is disconnected from the port of the second network element; and amanagement system communicatively coupled to the first network elementand the second network element; wherein the management system isconfigured to generate a first work order comprising a first work orderstep specifying that the port of the first network element is to bedisconnected from the port of the second network element; and whereinthe management system is configured to update information maintained bythe management system to indicate that the specified port of the firstnetwork element has been disconnected from the specified port of thesecond network element if the management system receives a messageindicating that a disconnection was detected at the specified port ofthe first network element during a period in which the first work orderstep of the first work order was expected to be performed and receives amessage indicating that a disconnection was detected at the specifiedport of the second network element during the period in which the firstwork order step of the first work order was expected to be performed.

Example 18 includes a program product for identify a connection betweena specified port of a first network element and a specified port of asecond network element, tangibly stored on a non-transitory storagemedium, comprising instructions operable to cause at least oneprogrammable processor to: generate a work order comprising a work orderstep specifying that the specified port of the first network element isto be connected to the specified port of the second network elementusing a cable; in connection with a connection being made at thespecified port of the first network element specified in the work orderstep, receiving information indicating that the connection has been madeat the specified port of the first network element; in connection with aconnection being made at the specified port of the second networkelement, receiving information indicating that the connection has beenmade at the specified port of the second network element; and ifinformation is received indicating that a connection has been made atthe specified port of the first network element during a period in whichthe work order step of the work order is expected to be performed andinformation is received indicating that a connection has been made atthe specified port of the second network element during the period inwhich the work order step of the work order is expected to be performed,updating connection information for the first network element and thesecond network element to indicate that the specified port of the firstnetwork element is connected to the specified port of the second networkelement.

Example 19 includes the program product of Example 18, wherein theinstructions are further operable to cause the at least one programmableprocessor to: generate a second work order comprising a second workorder step specifying that the specified port of the first networkelement is to be disconnected from the specified port of the secondnetwork element; in connection with a disconnection being made at thespecified port of the first network element, receiving informationindicating that the disconnection has been made at the specified port ofthe first network element; in connection with a disconnection being madeat the specified port of the second network element, receivinginformation indicating that the disconnection has been made at thespecified port of the second network element; and if information isreceived indicating that a disconnection has been made at the specifiedport of the first network element during a period in which the secondwork order step of the second work order was expected to be performedand information is received indicating that a disconnection has beenmade at the specified port of the second network element during theperiod in which the second work order step of the second work order wasexpected to be performed, updating connection information for the firstnetwork element and the second network element to indicate that thespecified port of the first network element is disconnected from thespecified port of the second network element.

Example 20 includes the program product of any of the Examples 18-19,wherein the instructions are further operable to cause the at least oneprogrammable processor to: send the first work order to a mobile device.

What is claimed is:
 1. A method comprising: generating a first workorder comprising a first work order step specifying that a port of afirst network element is to be connected to a port of a second networkelement using a cable; detecting, using the first network element, whena connection is made at the specified port of the first network elementusing the cable, and reading physical layer information about the cablefrom a first connector of the cable; and determining, by an electronicwork order application, if connection of the cable to the first networkelement complies with the first work order based on the physical layerinformation read from the first connector.
 2. The method of claim 1,further comprising, altering a visual indicator at the specified port ofthe first network element in response to determining that connection ofthe cable to the first network element complies with the first workorder.
 3. The method of claim 1, further comprising: detecting, usingthe second network element, when a connection is made at the specifiedport of the second network element, and reading the physical layerinformation about the cable from a second connector of the cable; anddetermining, by an electronic work order application, if connection ofthe cable to the second network element complies with the first workorder based on the physical layer information read from the secondconnector.
 4. The method of claim 1, wherein the first network elementand the second network element comprise first and second managed networkelements, respectively.
 5. The method of claim 1, wherein the first andsecond network elements comprise at least one of a patch panel, anoptical distribution frame, a splitter tray, a switch, and a router. 6.The method of claim 1, wherein each of the first and second networkelements includes at least one of EEPROM-based PLM technology and RFIDPLM technology.
 7. The method of claim 1, wherein the cable comprises atleast one of a fiber optic cable and a copper cable.
 8. The method ofclaim 1, wherein the physical layer information comprises an identifier.9. The method of claim 1, wherein the cable comprises a storage devicethat stores the physical layer information.
 10. The method of claim 3,further comprising, altering a visual indicator at the specified port ofthe second network element in response to determining that connection ofthe cable to the first network element complies with the first workorder.
 11. A system comprising: a first network element comprising atleast one port, wherein the first network element is configured todetect when a cable is connected to the port of the first networkelement; a second network element comprising at least one port, whereinthe second network element is configured to detect when a cable isconnected to the port of the second network element; and a managementsystem communicatively coupled to the first network element and thesecond network element; wherein the management system is configured togenerate a first work order comprising a first work order stepspecifying that the port of a first network element is to be connectedto the port of the second network element using the cable; wherein themanagement system is configured to detect, using the first networkelement, when a connection is made at the specified port of the firstnetwork element using the cable, and read physical layer informationabout the cable from a first connector of the cable; and wherein themanagement system is configured to determine if connection of the cableto the first network element complies with the first work order based onthe physical layer information read from the first connector.
 12. Thesystem of claim 11, further comprising a visual indicator at thespecified port of the first network element, wherein the managementsystem is configured to alter the visual indicator at the specified portof the first network element in response to determining that connectionof the cable to the first network element complies with the first workorder.
 13. The system of claim 11, further comprising: wherein themanagement system is configured to detect, using the second networkelement, when a connection is made at the specified port of the secondnetwork element, and read the physical layer information about the cablefrom a second connector of the cable; and wherein the management systemis configured to determine if connection of the cable to the secondnetwork element complies with the first work order based on the physicallayer information read from the second connector.
 14. The system ofclaim 11, wherein the cable comprises at least one of a fiber opticcable and a copper cable.
 15. The system of claim 11, wherein the firstnetwork element and the second network element comprise first and secondmanaged network elements, respectively.
 16. The system of claim 11,wherein the first and second network elements comprise at least one of apatch panel, an optical distribution frame, a splitter tray, a switch,and a router.
 17. The system of claim 11, wherein each of the first andsecond network elements includes at least one of EEPROM-based PLMtechnology and RFID PLM technology.
 18. The system of claim 11, whereinthe physical layer information comprises an identifier.
 19. The systemof claim 11, wherein the cable comprises a storage device that storesthe physical layer information.
 20. The system of claim 13, furthercomprising a visual indicator at the specified port of the secondnetwork element, wherein the management system is configured to alterthe visual indicator at the specified port of the second network elementin response to determining that connection of the cable to the firstnetwork element complies with the first work order.